Skip to content

Fix #166: Handle lack of Script Analyzer binaries #167

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 24, 2016

Conversation

daviwil
Copy link
Contributor

@daviwil daviwil commented Feb 24, 2016

This change enables PowerShell Editor Services to operate correctly in the
scenario where no Script Analyzer binaries are available. This is a first
step in the direction of removing the direct dependency on Script Analyzer
and moving analysis behavior to the new extensibility model.

This change enables PowerShell Editor Services to operate correctly in the
scenario where no Script Analyzer binaries are available.  This is a first
step in the direction of removing the direct dependency on Script Analyzer
and moving analysis behavior to the new extensibility model.
@daviwil daviwil force-pushed the daviwil/handle-no-script-analyzer branch from 02adfd9 to ded73de Compare February 24, 2016 18:56
daviwil added a commit that referenced this pull request Feb 24, 2016
…yzer

Fix #166: Handle lack of Script Analyzer binaries
@daviwil daviwil merged commit 451dcec into master Feb 24, 2016
@daviwil daviwil deleted the daviwil/handle-no-script-analyzer branch March 26, 2016 15:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants